What does this do?
This moves the report config for the new NAGPRA reports into the core and anthro tenant bindings. By doing this we ensure that the reports are only available for those tenants, as they are the only tenants with the procedures enabled for those reports.

Why are we doing this? (with JIRA link)
Jira: https://collectionspace.atlassian.net/browse/DRYD-1687

In tenants other than core/anthro, the NAGPRA reports can be selected from the Tools > Reports interface. This has a modal which allows a user to select records to run the report on with a record type that does not exist in the tenant, and as such causes an error in the ui. Ideally we need error handling in the ui as well, but for the time being we've decided to fix things here for now.

How should this be tested? Do these changes have associated tests?

• Build collectionspace without any changes
• Save the files in ${CSPACE_JEE_SERVER}/cspace/config/services/tenants/
• Rebuild collectionspace with the changes
• Diff the merged tenant bindings, e.g.

git diff -w --no-index materials/tenant-bindings.merged.xml ~/tmt/saved-bindings/materials/tenant-bindings.merged.xml

Dependencies for merging? Releasing to production?
None

Has the application documentation been updated for these changes?
No

Did someone actually run this code to verify it works?
@mikejritter ran the build and compared the tenant bindings